Technologies for remote device emulation

ABSTRACT

Technologies for facilitating communication between a master programmable logic controller and one or more target drives are disclosed. In an illustrative embodiment, a remote device emulation appliance is configured to receive a communication from a master programmable logic controller that is formatted according to a remote input/output protocol unusable by the target drive. The remote device emulation appliance converts the communication from the remote input/output protocol to a drive protocol usable by the target drive to control operations of the drive and transmits the converted communication to the target drive. The remote device emulation appliance may also convert communications received from the target drive from the drive protocol usable by the target drive to the remote input/output protocol and transmit such converted communications to the master programmable logic controller.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/210,200, filed Aug. 26, 2015, the entiredisclosure of which is incorporated by reference herein.

BACKGROUND

Programmable logic controllers are computer systems used in a variety ofapplications to control automation of various machines. For example,programmable logic controllers are often used in industrialapplications, such as assembly lines or other processes, to control theoperation of motors, actuators, robotic machines, and other outputdevices. Additionally, to facilitate the control of such machines,programmable logic controllers are often coupled to an array of sensorsto receive various sensor data, which may provide an amount of closedloop feedback for the control of the various machines. Due to the oftenharsh environment of the typical applications in which programmablelogic controller are used, most programmable logic controllers aredesigned and built to operate in severe conditions (e.g., excessivedirt, heat, cold, vibrations, etc.)

Typical programmable logic controllers control the operation of theassociated output devices based on a software program. As the namesuggests, the software programs executed by programmable logiccontrollers may be modified or updated to customize the programmablelogic controller for a specific purpose or adjust for new or differentoutput devices, sensors, and/or other devices controlled by or otherwisein communication with the programmable logic controller.

Although programmable logic controllers are reprogrammable, modificationof the software program can be difficult and time extensive. Suchdifficulty increases over time as the programmable logic controllerbecomes coupled to additional output devices, input sensors, and otherlogic controllers. Additionally, an owner's knowledge of the originalsoftware program may diminish or become nonexistent over time. As such,it can become difficult to update components of a control system. Forexample, updating a legacy output device with a newer output device,which may use different communication format and/or protocol relative tothe legacy output device, may require the software program executed bythe programmable logic controller to be redesigned to successfullycommunicate with the new output device. As mentioned above, suchreprogramming can be costly and take a significant amount of time duringwhich the assembly line or other industrial application is non-operativeresulting in additional losses for the company or owner.

SUMMARY

According to one aspect, a method for facilitating communication betweena master programmable logic controller and a target drive may includereceiving, by a remote device emulation appliance, a first communicationfrom the master programmable logic controller over a remote input/outputcommunication link, wherein the first communication is formattedaccording to a remote input/output protocol unusable by the targetdrive; converting, by the remote device emulation appliance, the firstcommunication from the remote input/output protocol to a drive protocolusable by the target drive; and transmitting, by the remote deviceemulation appliance, the converted communication to the target drive tocontrol an operation of the target drive.

In some embodiments, receiving the first communication may includereceiving, by the remote device emulation appliance, a communicationfrom a remote input/output scanner of the master programmable logiccontroller. Additionally, in some embodiments, converting the firstcommunication may include converting, by the remote device emulationappliance, the communication from a remote input/output protocolconfigured for use by a legacy drive to the drive protocol usable by thetarget drive.

In some embodiments, converting the first communication may includeconverting, by the remote device emulation appliance, a format of acontrol word included in the first communication from a legacy driveformat usable by a legacy drive to a target drive format usable by thetarget drive. In such embodiments, converting the first communicationmay include retrieving, by the remote device emulation appliance,communication conversion data and converting the format of the controlword from the legacy drive format to the target drive format based onthe communication conversion data. The communication conversion data maydefine a set of rules for converting the format of the control word tothe target drive format. Additionally, in such embodiments, convertingthe format of the control word may include generating a convertedcontrol word based on the target drive format and transmitting theconverted communication may include transmitting the converted controlwork to the target drive.

In some embodiments, converting the first communication may includeconverting, by the remote device emulation appliance, drive operationalparameters included in the communication from a legacy drive formatusable by a legacy drive to a target drive format usable by the targetdrive. In such embodiments, converting the first communication mayinclude retrieving, by the remote device emulation appliance,communication conversion data and converting the drive operationalparameters from the legacy drive format to the target drive format basedon the communication conversion data. The communication conversion datamay define a set of rules for converting the drive operationalparameters to the target drive format. Additionally, in suchembodiments, converting the drive operational parameters may includegenerating converted drive operational parameters based on the targetdrive format and transmitting the converted communication may includetransmitting the converted drive operational parameters to the targetdrive.

In some embodiments, the converted communication may include a firstconverted communication and the method may also include receiving, bythe remote device emulation appliance, a second communication from thetarget drive in response to the first converted communication, whereinthe second communication is formatted according to the drive protocol;converting, by the remote device emulation appliance, the secondcommunication from the drive protocol to the remote input/outputprotocol; and transmitting the converted second communication to themaster programmable logic controller. In such embodiments, convertingthe second communication may include converting, by the remote deviceemulation appliance, a format of a status word included in the secondcommunication from a target drive format usable by the target drive to alegacy drive format usable by a legacy drive. Additionally, in suchembodiments, converting the second communication may include retrieving,by the remote device emulation appliance, communication conversion dataand converting the format of the status word from the target driveformat to the legacy drive format based on the communication conversiondata. The communication conversion data may define a set of rules forconverting the format of the status word to the legacy drive format. Insuch embodiments, converting the format of the status word may includegenerating a converted status word based on the legacy drive format andtransmitting the converted second communication may include transmittingthe converted status word to the master programmable logic controller.Additionally, in such embodiments, converting the second communicationmay include converting, by the remote device emulation appliance, driveoperational parameters included in the second communication from atarget drive format usable by the target drive to a legacy drive formatusable by a legacy drive. In those embodiments, converting the secondcommunication may include retrieving, by the remote device emulationappliance, communication conversion data and converting the driveoperational parameters from the target drive format to the legacy driveformat based on the communication conversion data. The communicationconversion data may define a set of rules for converting the format ofthe drive operational parameters to the legacy drive format.Additionally, in such embodiments, converting the drive operationalparameters may include generating converted drive operational parametersbased on the legacy drive format and transmitting the converted secondcommunication may include transmitting the converted drive operationalparameters to the master programmable logic controller.

Additionally, in some embodiments, the method may also includereceiving, by the remote device emulation appliance, an alias name forthe target drive from a user of the remote device emulation applianceand setting, by the remote device emulation appliance, a name of thetarget drive to the alias name. Additionally, the method may includereceiving, by the remote device emulation appliance, a selection of atype of the target drive; retrieving, by the remote device emulationappliance, configuration data from a data storage of the remote deviceemulation appliance, the configuration data comprising default settingsfor drive operational parameters of the target drive; and setting, bythe remote device emulation appliance and in response to the selection,the drive operational parameters of the target drive based on theconfiguration data. Additionally or alternatively, the method mayinclude receiving, by the remote device emulation appliance, a selectionof a type of the target drive; receiving, by the remote device emulationappliance, configuration data from a user of the remote device emulationappliance, the configuration data comprising settings for driveoperational parameters of the target drive; and setting, by the remotedevice emulation appliance, the drive operational parameters of thetarget drive based on the received configuration data. In suchembodiments, the method may further include determining, by the remotedevice emulation appliance, whether each of the set drive operationalparameters is valid and visually identifying a first drive operationalparameter of the set drive operational parameters in response to adetermination that the first drive operational parameter is invalid.

In some embodiments, the method may also include receiving, by theremote device emulation appliance, a selection of a legacy drive to beemulated by the target drive and retrieving, by the remote deviceemulation appliance, communication conversion data based on the selectedlegacy drive, wherein the communication conversion data definesconversion parameters for converting a communication from a legacy driveformat useable by the legacy drive to a target drive format usable bythe target drive. In such embodiments, the communication conversion datamay include control word format conversion parameters to convert acontrol word format from the legacy drive format to the target driveformat and status word format conversion parameters to convert a statusword format from the legacy drive format to the target drive format.Additionally, in such embodiments, the method may further includereceiving, by the remote device emulation appliance, user-definedconversion parameters from a user and setting, by the remote deviceemulation appliance, configurable conversion parameters of thecommunication conversion data based on the user-defined conversionparameters.

According to another aspect, a remote device emulation appliance forfacilitating communication between a master programmable logiccontroller and a drive may include a communication circuitry and acommunication conversion circuitry. The communication circuity may beconfigured to receive a first communication from the master programmablelogic controller over a remote input/output communication link, whereinthe first communication is formatted according to a remote input/outputprotocol unusable by the target drive. The communication conversioncircuity may be configured to convert the first communication from theremote input/output protocol to a drive protocol usable by the targetdrive. Additionally, the communication circuity may be configured totransmit the converted communication to the target drive to control anoperation of the target drive.

In some embodiments, the communication circuity may be configured toreceive the first communication from a remote input/output scanner ofthe master programmable logic controller. Additionally, in someembodiments, to convert the first communication may include to convertthe first communication from a remote input/output protocol configuredfor use by a legacy drive to the drive protocol usable by the targetdrive. In some embodiments, to convert the first communication mayinclude to convert a format of a control word included in the firstcommunication from a legacy drive format usable by a legacy drive to atarget drive format usable by the target drive. In such embodiments, thecommunication conversion circuity may be configured to retrievecommunication conversion data and convert the format of the control wordfrom the legacy drive format to the target drive format based on thecommunication conversion data, wherein the communication conversion datadefines a set of rules for converting the format of the control word tothe target drive format. Additionally, in such embodiments, to convertthe format of the control word may include to generate a convertedcontrol word based on the target drive format and to transmit theconverted communication may include to transmit the converted controlwork to the target drive.

Additionally, in some embodiments, to convert the first communicationmay include to convert drive operational parameters included in thecommunication from a legacy drive format usable by a legacy drive to atarget drive format usable by the target drive. In such embodiments, toconvert the first communication may include to retrieve communicationconversion data and convert the drive operational parameters from thelegacy drive format to the target drive format based on thecommunication conversion data, and the communication conversion data maydefine a set of rules for converting the drive operational parameters tothe target drive format. Additionally, in such embodiments, to convertthe drive operational parameters may include to generate converted driveoperational parameters based on the target drive format and to transmitthe converted communication may include to transmit the converted driveoperational parameters to the target drive.

In some embodiments, the converted communication may include a firstconverted communication. In such embodiments, the communication circuitymay be configured to receive a second communication from the targetdrive in response to the first converted communication, wherein thesecond communication is formatted according to the drive protocol, thecommunication conversion circuity may be configured to convert thesecond communication from the drive protocol to the remote input/outputprotocol, and the communication circuity may be further configured totransmit the converted second communication to the master programmablelogic controller. Additionally, in such embodiments, to convert thesecond communication may include to convert a format of a status wordincluded in the second communication from a target drive format usableby the target drive to a legacy drive format usable by a legacy drive.Further, in such embodiments, to convert the second communication mayinclude to retrieve communication conversion data and convert the formatof the status word from the target drive format to the legacy driveformat based on the communication conversion data, and the communicationconversion data may define a set of rules for converting the format ofthe status word to the legacy drive format. Additionally, in suchembodiments, t convert the format of the status word may include togenerate a converted status word based on the legacy drive format and totransmit the converted second communication may include to transmit theconverted status word to the master programmable logic controller.Additionally, to convert the second communication may include to convertdrive operational parameters included in the second communication from atarget drive format usable by the target drive to a legacy drive formatusable by a legacy drive. In such embodiments, to convert the secondcommunication may include to retrieve communication conversion data andconvert the drive operational parameters from the target drive format tothe legacy drive format based on the communication conversion data, andthe communication conversion data may define a set of rules forconverting the format of the drive operational parameters to the legacydrive format. Additionally, in such embodiments, to convert the driveoperational parameters may include to generate converted driveoperational parameters based on the legacy drive format and to transmitthe converted second communication may include to transmit the converteddrive operational parameters to the master programmable logiccontroller.

Additionally, in some embodiments, the remote device emulation appliancemay further include an initialization circuity configured to receive analias name for the target drive from a user of the remote deviceemulation appliance and set a name of the target drive to the aliasname. Additionally, in some embodiments, the remote device emulationappliance may further include an initialization circuity configured toreceive a selection of a type of the target drive; retrieveconfiguration data from a data storage of the remote device emulationappliance, the configuration data comprising default settings for driveoperational parameters of the target drive; and set, in response to theselection, the drive operational parameters of the target drive based onthe configuration data. Additionally or alternatively, the remote deviceemulation appliance may further include an initialization circuityconfigured to receive a selection of a type of the target drive; receiveconfiguration data from a user of the remote device emulation appliance,the configuration data comprising settings for drive operationalparameters of the target drive; and set the drive operational parametersof the target drive based on the received configuration data.

In some embodiments, the remote device emulation appliance may also avalidation circuity configured to determine whether each of the setdrive operational parameters is valid and visually identify a firstdrive operational parameter of the set drive operational parameters inresponse to a determination that the first drive operational parameteris invalid. Additionally, in some embodiments, the remote deviceemulation appliance may further an initialization circuity configured toreceive a selection of a legacy drive to be emulated by the target driveand retrieve communication conversion data based on the selected legacydrive, and the communication conversion data may define conversionparameters for converting a communication from a legacy drive formatuseable by the legacy drive to a target drive format usable by thetarget drive. In such embodiments, the communication conversion data mayinclude control word format conversion parameters to convert a controlword format from the legacy drive format to the target drive format andstatus word format conversion parameters to convert a status word formatfrom the legacy drive format to the target drive format. Additionally,in such embodiments, the initialization circuity may be furtherconfigured to receive, user-defined conversion parameters from a userand set configurable conversion parameters of the communicationconversion data based on the user-defined conversion parameters.

According to a further aspect, one or more non-transitory,machine-readable storage media comprising a plurality of instructionsstored thereon that, in response to execution, may cause a remote deviceemulation appliance to receive a first communication from a masterprogrammable logic controller over a remote input/output communicationlink, wherein the first communication is formatted according to a remoteinput/output protocol unusable by the target drive; convert the firstcommunication from the remote input/output protocol to a drive protocolusable by the target drive; and transmit the converted communication tothe target drive to control an operation of the target drive.

In some embodiments, to receive the first communication may include toreceive the first communication from a remote input/output scanner ofthe master programmable logic controller. Additionally, in someembodiments, to convert the first communication may include to convertthe first communication from a remote input/output protocol configuredfor use by a legacy drive to the drive protocol usable by the targetdrive. Additionally or alternatively, to convert the first communicationmay include to convert a format of a control word included in the firstcommunication from a legacy drive format usable by a legacy drive to atarget drive format usable by the target drive. In such embodiments, toconvert the first communication may include to retrieve communicationconversion data and convert the format of the control word from thelegacy drive format to the target drive format based on thecommunication conversion data, wherein the communication conversion datadefines a set of rules for converting the format of the control word tothe target drive format. Additionally, in such embodiments, to convertthe format of the control word may include to generate a convertedcontrol word based on the target drive format and to transmit theconverted communication may include to transmit the converted controlwork to the target drive.

Additionally, in some embodiments, to convert the first communicationmay include to convert drive operational parameters included in thecommunication from a legacy drive format usable by a legacy drive to atarget drive format usable by the target drive. In such embodiments, toconvert the first communication may include to retrieve communicationconversion data and convert the drive operational parameters from thelegacy drive format to the target drive format based on thecommunication conversion data, wherein the communication conversion datadefines a set of rules for converting the drive operational parametersto the target drive format. Additionally, in such embodiments, toconvert the drive operational parameters may include to generateconverted drive operational parameters based on the target drive formatand to transmit the converted communication may include to transmit theconverted drive operational parameters to the target drive.

In some embodiments, the converted communication may include a firstconverted communication. In such embodiments, the plurality ofinstructions may further cause the remote device emulation appliance toreceive a second communication from the target drive in response to thefirst converted communication, wherein the second communication isformatted according to the drive protocol, convert the secondcommunication from the drive protocol to the remote input/outputprotocol, and transmit the converted second communication to the masterprogrammable logic controller. Additionally, in such embodiments, toconvert the second communication may include to convert a format of astatus word included in the second communication from a target driveformat usable by the target drive to a legacy drive format usable by alegacy drive. Further, in such embodiments, to convert the secondcommunication may include to retrieve communication conversion data andconvert the format of the status word from the target drive format tothe legacy drive format based on the communication conversion data, andthe communication conversion data may define a set of rules forconverting the format of the status word to the legacy drive format.Additionally or alternatively, in such embodiments, to convert theformat of the status word may include to generate a converted statusword based on the legacy drive format and to transmit the convertedsecond communication may include to transmit the converted status wordto the master programmable logic controller. Additionally, to convertthe second communication may include to convert drive operationalparameters included in the second communication from a target driveformat usable by the target drive to a legacy drive format usable by alegacy drive. In such embodiments, to convert the second communicationmay include to retrieve communication conversion data and convert thedrive operational parameters from the target drive format to the legacydrive format based on the communication conversion data, and thecommunication conversion data may define a set of rules for convertingthe format of the drive operational parameters to the legacy driveformat. Further, in such embodiments, to convert the drive operationalparameters may include to generate converted drive operationalparameters based on the legacy drive format and to transmit theconverted second communication may include to transmit the converteddrive operational parameters to the master programmable logiccontroller.

Additionally, in some embodiments, the plurality of instructions mayfurther cause the remote device emulation appliance to receive an aliasname for the target drive from a user of the remote device emulationappliance and set a name of the target drive to the alias name.Additionally or alternatively, the plurality of instructions may furthercause the remote device emulation appliance to receive a selection of atype of the target drive; retrieve configuration data from a datastorage of the remote device emulation appliance, the configuration datacomprising default settings for drive operational parameters of thetarget drive; and set, in response to the selection, the driveoperational parameters of the target drive based on the configurationdata. Additionally or alternatively, the plurality of instructions mayfurther cause the remote device emulation appliance to receive aselection of a type of the target drive; receive configuration data froma user of the remote device emulation appliance, the configuration datacomprising settings for drive operational parameters of the targetdrive; and set the drive operational parameters of the target drivebased on the received configuration data. In such embodiments, theplurality of instructions may further cause the remote device emulationappliance to determine whether each of the set drive operationalparameters is valid and visually identify a first drive operationalparameter of the set drive operational parameters in response to adetermination that the first drive operational parameter is invalid.

In some embodiments, the plurality of instructions may also cause theremote device emulation appliance to receive a selection of a legacydrive to be emulated by the target drive and retrieve communicationconversion data based on the selected legacy drive, and thecommunication conversion data may define conversion parameters forconverting a communication from a legacy drive format useable by thelegacy drive to a target drive format usable by the target drive. Insuch embodiments, the communication conversion data may include controlword format conversion parameters to convert a control word format fromthe legacy drive format to the target drive format and status wordformat conversion parameters to convert a status word format from thelegacy drive format to the target drive format. Additionally, in suchembodiments, the plurality of instructions further cause the remotedevice emulation appliance to receive, user-defined conversionparameters from a user and set configurable conversion parameters of thecommunication conversion data based on the user-defined conversionparameters.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of acontrol system for controlling operation of industrial drives;

FIG. 2 is a simplified block diagram of at least one embodiment of aremote device emulation appliance of the system of FIG. 1;

FIG. 3 is a simplified block diagram of at least one embodiment of anenvironment that may be established by the remote device emulationappliance of FIG. 2;

FIGS. 4-6 is a simplified flow diagram of at least one embodiment of amethod for configuring a drive of the control system of FIG. 1 that maybe executed by the remote device emulation appliance of FIGS. 2 and 3;

FIGS. 7-10 are illustrative screenshots of a user interface that may begenerated by the remote device emulation appliance of FIGS. 2 and 3during execution of the method of FIGS. 4-6;

FIG. 11 is a simplified flow diagram of at least one embodiment of amethod for configuring drive emulation that may be executed by theremote device emulation appliance of FIGS. 2 and 3;

FIG. 12 is an illustrative screenshot of a user interface that may begenerated by the remote device emulation appliance of FIGS. 2 and 3during execution of the method of FIG. 11; and

FIG. 13 is a simplified flow diagram of at least one embodiment of amethod for facilitating communication between a master programmablelogic controller and a target drive of the system of FIG. 1, which maybe executed by the remote device emulation appliance of FIGS. 2 and 3.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described. Additionally, it should be appreciated that itemsincluded in a list in the form of “at least one A, B, and C” can mean(A); (B); (C): (A and B); (B and C); (A and C); or (A, B, and C).Similarly, items listed in the form of “at least one of A, B, or C” canmean (A); (B); (C): (A and B); (B and C); (A or C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon one or more transitory or non-transitory machine-readable (e.g.,computer-readable) storage medium, which may be read and executed by oneor more processors. A machine-readable storage medium may be embodied asany storage device, mechanism, or other physical structure for storingor transmitting information in a form readable by a machine (e.g., avolatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

Referring now to FIG. 1, a system 100 for controlling operation of anumber of industrial drives includes one or more remote device emulationappliances 102, a master programmable logic controller (PLC) 104, andone or more drives 106 managed or controlled by a respective remotedevice emulation appliance 102. The remote device emulation appliance102 is communicatively coupled to the master programmable logiccontroller 104 via a remote input/output communication link 110 and toeach managed drive 106 via a corresponding control link 112. In use, theremote device emulation appliance 102 is configured to convertcommunications between the master programmable logic controller 104 andeach drive 106 to facilitate control of the corresponding drive 106. Assuch, newer drives 106 and/or drives 106 not configured for use with themaster programmable logic controller 104, and the control softwareprogram executed by the controller 104, may be used with the masterprogrammable logic controller 104 without the requirement ofreprogramming the controller 104.

As discussed in more detail below, the remote device emulation appliance102 may be configured to emulate a legacy drive (e.g., an older drivefor which the master programmable logic controller 104 is currentlyprogrammed to control) by converting the various communications. Thedrive emulation performed by the remote device emulation appliance 102may allow the use of newer drives 106 having advanced features and/orfunctionality to be used in the system 100 without rewiring orreprogramming of the master programmable logic controller 104 and thesystem 100. In some embodiments, for example, the remote deviceemulation appliance 102 may be configured to convert a communicationreceived from the master programmable logic controller 104 from a remoteinput/output protocol usable by a legacy drive to a drive protocolusable by a target drive 106 to which the communication is directed.Additionally or alternatively, the remote device emulation appliance 102may be configured to convert communications received from the targetdrive 106 from the drive protocol usable by the target drive 106 to aremote input/output protocol usable by the legacy drive for transmissionto the master programmable logic controller 104. For example, the remotedevice emulation appliance 102 may convert a format of a control word ofa communication received from the master programmable logic controller104 from a legacy drive format usable by a legacy drive to a driveformat usable by the target drive 106. Similarly, the remote deviceemulation appliance 102 may convert a format of a status word of acommunication received from a target drive 106 from the drive formatusable by the target drive 106 to the legacy drive format usable by alegacy drive. In a similar manner, the remote device emulation appliance102 may convert drive operational parameters for controlling a targetdrive 106 from the legacy drive format to the drive format usable by thetarget drive 106 and/or from the drive format to the legacy drive formatas discussed in more detail below.

The remote device emulation appliance 102 may be embodied as any type ofPLC communication device, network appliance, or other computing devicecapable of converting communications and performing the functionsdescribed herein. As shown in FIG. 2, the illustrative remote deviceemulation appliance 102 includes a processor 210, an I/O subsystem 212,a memory 214, a communication circuit 220, a data storage 222, one ormore output devices 224, a reset device 226, an input communication port230, output communication port 232, a control output port 240, and anetwork port 250. Of course, the remote device emulation appliance 102may include other or additional components, such as those commonly foundin a network appliance (e.g., various input/output devices), in otherembodiments. Additionally, in some embodiments, one or more of theillustrative components may be incorporated in, or otherwise form aportion of, another component. For example, the memory 214, or portionsthereof, may be incorporated in the processor 210 in some embodiments

The processor 210 may be embodied as any type of processor capable ofperforming the functions described herein. For example, the processor210 may be embodied as a single or multi-core processor(s), a single ormulti-socket processor, a digital signal processor, a microcontroller,or other processor or processing/controlling circuit. Similarly, thememory 214 may be embodied as any type of volatile or non-volatilememory or data storage capable of performing the functions describedherein. In operation, the memory 214 may store various data and softwareused during operation of the remote device emulation appliance 102 suchas operating systems, applications, programs, libraries, and drivers.The memory 214 is communicatively coupled to the processor 210 via theI/O subsystem 212, which may be embodied as circuitry and/or componentsto facilitate input/output operations with the processor 210, the memory214, and other components of the remote device emulation appliance 102.For example, the I/O subsystem 212 may be embodied as, or otherwiseinclude, memory controller hubs, input/output control hubs, firmwaredevices, communication links (i.e., point-to-point links, bus links,wires, cables, light guides, printed circuit board traces, etc.) and/orother components and subsystems to facilitate the input/outputoperations. In some embodiments, the I/O subsystem 212 may form aportion of a system-on-a-chip (SoC) and be incorporated, along with theprocessor 210, the memory 214, and other components of the remote deviceemulation appliance 102, on a single integrated circuit chip.

The communication circuit 220 may be embodied as any communicationcircuit, device, or collection thereof, capable of enablingcommunications between the remote device emulation appliance 102 and themaster programmable logic controller 104 and the drives 106, as well asother appliances 102 and/or remote computing devices 170 (see FIG. 2) asdiscussed in more detail below. To do so, the communication circuit 220may be configured to use any one or more communication technology andassociated protocols (e.g., Ethernet, Bluetooth®, Wi-WiMAX, etc.) toeffect such communication, including wired and/or wireless communicationtechnology and associated protocols.

The data storage 222 may be embodied as any type of device or devicesconfigured for the short-term or long-term storage of data. For example,the data storage 222 may include any one or more memory devices andcircuits, memory cards, hard disk drives, solid-state drives, or otherdata storage devices. In the illustrative embodiment, the data storage222 stores a communication conversion database 320 (see FIG. 3). Thecommunication conversion database 320 includes a set of rules ordefinitions usable by the remote device emulation appliance 102 toconvert communications from the remote input/output protocol (e.g., alegacy drive protocol) to the drive protocol usable by the drives 106and/or from the drive protocol usable by the drives 106 to the remoteinput/output protocol (e.g., the legacy drive protocol). For example,the communication conversion database 320 may include conversion rulesfor converting a control word, a status word, and/or drive operationalparameters from one format (e.g., the legacy drive protocol or the driveprotocol usable by the drives 106) to another format (e.g., to the driveprotocol usable by the drives 106 or the legacy drive protocol). Itshould be appreciated that the communication conversion database 320 mayinclude multiple sets of rules for different types of drives 106 tofacilitate the addition of new drive types to the system 100.

The output devices 224 may include any number and type of output devicescapable of providing information to a user of the remote deviceemulation appliance 102. For example, the output devices 224 may beembodied as visual, audible, and/or tactile output devices. In theillustrative embodiment, the output devices 224 include one or morelight emitting diodes 228 configured to provide visual information tothe user. Of course, in other embodiments, other types of visual,audible, and/or tactile output devices may be used such as a displayscreen or audible alert device.

The reset device 226 may be embodied as any type of user-selectabledevice, such as a push-button switch, a toggle switch, or other switchor device. In use, a user of the remote device emulation appliance 102may activate the reset device 226 to cause the remote device emulationappliance 102 to reset various options to default settings. For example,activation of the reset device 226 may cause the remote device emulationappliance 102 to set the communication conversion data used to convertcommunications to a default set of conversion rules and/or driveoperational parameters. In this way, a user of the remote deviceemulation appliance 102 may reset the appliance 102 to safe, factorydefault values in the event that the remote device emulation appliance102 is inadvertently set to erroneous or adverse settings.

The input communication port 230 is configured for connection to theremote input/output communication link 110 to facilitate communicationswith the master programmable logic controller 104. In the illustrativeembodiment, the input communication port 230 is embodied as a 3-wireRemote Input/Output (RIO) terminal block configured for connection to a3-wire remote input/output communication link 110. Of course, the inputcommunication port 230 may have a different structure and/or features inother embodiments based on the type and features of the remoteinput/output communication link 110 and communication modality of themaster programmable logic controller 104.

The input communication port 230 is also communicatively coupled to theoutput communication port 232 via a communication interconnect 234. Theinterconnection of the ports 230, 232 allow connection of multipleremote device emulation appliances in a daisy-chain manner usingadditional remote input/output communication links 110. For example, asshown in FIG. 1, the leftmost remote device emulation appliance 102 hasan input communication port 230 communicatively coupled to the masterprogrammable logic controller 104 via the remote input outputcommunication link 110 and an output communication port 232communicatively coupled to another remote device emulation appliance 102via another remote input output communication link 110. Although notshown in FIG. 1, additional remote device emulation appliances 102 maybe coupled in such manner to facilitate the control of additional drives106. Similar to the input communication port 230, the outputcommunication port 232 is illustratively embodied as a 3-wire RemoteInput/Output (RIO) terminal block configured for connection to a 3-wireremote input/output communication link 110.

The control output port 240 is configured for connection to one or moredrives 106 to control the operation of the drives 106. In theillustrative embodiment, the control output port 240 is embodied as anRS-232 terminal block for connection to a control link 112. In someembodiments, one or more adapters may be used in conjunction with thecontrol output port 240 depending on the structure and functionality ofthe control link 112. Additionally, as shown in FIG. 1, the controloutput port 240 may be coupled to multiple drives 106. For example, inthe illustrative embodiment, up to six drives 106 may be coupled to thecontrol output port 240.

The network port 250 is configured for connection to a remote computer170 as shown in FIG. 1 to facilitate configuration of the remote deviceemulation appliance 102 as discussed in more detail below. In theillustrative embodiment, the network port 250 is embodied as an Ethernetport configured to mate with RJ-45 type connectors. Of course, thenetwork port 250 may be embodied as other types of communication portsconfigured to mate with different connectors in other embodiments basedon the particular communication protocol to be used. In the illustrativeembodiment, the remote device emulation appliance 102 includes a singlenetwork port 250; however, in other embodiments, the remote deviceemulation appliance 102 may include additional communication ports 252,which may be similar or different from the network port 250.

Referring back to FIG. 1, the master programmable logic controller 104may be embodied as any type of programmable logic controller configuredfor remote input/output operation. In the illustrative embodiment, themaster programmable logic controller 104 includes a programmable logiccontroller module 120 and one or more RIO scanner modules 122. Ofcourse, in other embodiments, the master programmable logic controller104 may include additional or other modules and/or devices. For example,in some embodiments, the master programmable logic controller 104 mayinclude multiple ports for receiving various modules, such as additionalscanner modules, control modules, and/or the other PLC modules.

The programmable logic controller module 120 may be embodied as any typeof programmable logic controller capable of controlling industrialdrives. Similarly, the RIO scanners 122 may be embodied as any type ofremote I/O scanners capable of transmitting and receiving communicationsfrom remote input/output modules, including the remote device emulationappliance 102. As discussed above, the master programmable logiccontroller 104 (i.e., the PLC module 120) may be programmed andconfigured for controlling legacy drives and/or drives of a typedifferent from the drives 106. For example, the top-most RIO scanner 122of the illustrative master programmable logic controller 104 may becommunicatively coupled to one or more legacy RIO modules 130, which maycontrol one or more legacy drives 132 and/or legacy input/output devices134. That is, the master programmable logic controller 104 is programmedand configured to communicate with the legacy drives 132; however, theremote device emulation appliance 102 allows the master programmablelogic controller 104 to also communicate with the drives 106 asdiscussed in more detail below. As such, newer or different drives(i.e., the drives 106) may be added to the system 100 without thereprogramming of the master programmable logic controller 104 andwithout reconfiguring the system 100. As such, the system 100 mayinclude legacy drives 132 and newer or different drives 106. It shouldbe appreciated that the term “legacy drive” as used herein may refer todrives manufactured during a time period prior to the manufacture of thedrives 106, drives that are no longer supported by their correspondingmanufacturer, and/or drives that are otherwise different from the drives106 (e.g., different manufacturer or different type).

Referring now to FIG. 3, in use, each remote device emulation appliance102 may establish an environment 300. The illustrative environment 300includes a communication module 302, a configuration module 304, avalidation module 306, and a communication conversion module 308. Eachof the modules and other components of the environment 300 may beembodied as firmware, software, hardware, or a combination thereof. Forexample the various modules, logic, and other components of theenvironment 300 may form a portion of, or otherwise be established by,the processor 210, the I/O subsystem 212, an SoC, or other hardwarecomponents of the remote device emulation appliance 102. As such, insome embodiments, any one or more of the modules of the environment 300may be embodied as circuitry or a collection of electrical devices(e.g., a communication circuitry 302, a configuration circuitry 304, avalidation circuitry 306, a communication conversion circuitry 308,etc.).

The communication module 302 of the remote device emulation appliance102 facilitates communications between the remote device emulationappliance 102 and the master programmable logic controller 104 and thedrives 106 managed by the remote device emulation appliance 102. Forexample, the communication module 302 may facilitate communications fromthe master programmable logic controller 104 and/or other remote deviceemulation appliances 102 via the input communication port 230 and/or theoutput communication port 232. Similarly, the communication module 302may facilitate communication to one or more drives 106 via the controloutput port 240. Additionally, the communication module 302 mayfacilitate communications with the remote computer 170 and/or otherremote computing devices via the network port 250.

The configuration module 304 is configured to facilitate configurationand customization of the remote device emulation appliance 102. To doso, a user may utilize a remote computer 170 to communicate with theremote device emulation appliance 102 to configure the appliance 102,which is handled by the configuration module 304. For example, asdiscussed in more detail below, the configuration module 304 allows auser to configure various operational parameters of the drives 106,drive emulation parameters to emulate legacy drives, and/or otherconversion parameters for converting communications (e.g., control wordformat conversion parameters, status word format conversion parameters,etc.). Such configuration and/or conversion data may be stored in thecommunication conversion database 320 of the data storage 222 andsubsequently used to convert communications between the masterprogrammable logic controller 104 and the drives 106 as discussed inmore detail below.

The validation module 306 is configured to validate the various settingsand configurations implemented by the configuration module 304. Forexample, if a drive operational parameter is set outside an allowabletolerance of a particular drive, an unusable control format is selected,multiple drives are assigned to the same rack slot, and/or otherconfiguration error occurs, the validation module 306 is configured todetect such errors and notify the user. In this way, the validationmodule 306 validates the configuration of the remote device emulationappliance 102 prior to implementation of such configuration requests,allowing the user to change or confirm the settings or configuration. Inthe illustrative embodiment, the validation module 306 is configured tovisually identify (e.g., highlight) those settings deemed to be outsidea defined threshold or otherwise erroneous.

The communication conversion module 308 is configured to convertcommunications received from the master programmable logic controller104 and convert communications received from the drives 106. Forexample, as discussed in more detail below, the communication conversionmodule 308 may convert communications received from the masterprogrammable logic controller 104 from a remote input/output protocolusable by a legacy drive to a drive protocol usable by a target drive106 to which the communication is directed. Additionally oralternatively, the communication conversion module 308 may convertcommunications received from the target drive 106 from the driveprotocol usable by the target drive 106 to a remote input/outputprotocol usable by a legacy drive. For example, the communicationconversion module 308 may convert a format of a control word of acommunication received from the master programmable logic controller 104from a legacy drive format usable by a legacy drive to a drive formatusable by a target drive 106. Similarly, the communication conversionmodule 308 may convert a format of a status word of a communicationreceived from a target drive 106 from the drive format usable by atarget drive 106 to a legacy drive format usable by a legacy drive. In asimilar manner, the communication conversion module 308 may convertdrive operational parameters of a target drive 106 from the legacy driveformat to the drive format usable by the target drive 106 and/or fromthe drive format to the legacy drive format as discussed in more detailbelow.

Referring now to FIGS. 4-6, in use, the remote device emulationappliance 102 may execute a method 400 for configuring controlparameters of a drive 106 of the system 100. The method 400 begins withblock 402 in which the remote device emulation appliance 102 determineswhether a user has successfully logged into the remote device emulationappliance 102. As discussed above, a user may utilize a remote computer170 communicatively coupled to the network port 250 to communicate withthe remote device emulation appliance 102. In response to successfulcommunicative coupling, the remote device emulation appliance 102presents a user interface (e.g., user interface 700 of FIG. 7) to theuser via a suitable display device of the remote computer 170. The usermay log into the remote device emulation appliance 102 via the userinterface using any suitable user authentication scheme (e.g., password,passcode, biometric parameters, etc.).

If the remote device emulation appliance 102 successfully authenticatesthe user, the method 400 advances to block 404 in which the remotedevice emulation appliance 102 displays appliance information on theremote computer 170 via the user interface. The appliance informationmay include any type of information related to the remote deviceemulation appliance 102 such as the model number, part number, serialnumber, the machine access code (MAC) number, the present firmware andsoftware revision executed by the remote device emulation appliance 102,and/or other information describing aspects of the remote deviceemulation appliance 102 itself.

In block 406, the remote device emulation appliance 102 determineswhether a user desires to configure appliance settings. The appliancesettings may include any user-configurable setting or parameter of theremote device emulation appliance 102 including, for example,communication, drive settings, drive emulation settings, conversionparameters, and/or other configurable settings of the remote deviceemulation appliance 102. If so, the method 400 advances to block 408 inwhich the remote device emulation appliance 102 determines whether theuser desires to update or configure communication interface settings ofthe remote device emulation appliance 102 (e.g., based on user-suppliedinput or request). The communication interface settings may definevarious parameters or aspects of the underlying communication protocoland/or associated hardware used by the remote device emulation appliance102 to communicate with the master programmable logic controller 104and/or the drives 106. For example, in block 412, the remote deviceemulation appliance 102 may set the baud rate of the communicationsbased on a user selection or input. Additionally or alternatively, theremote device emulation appliance 102 may set the block transfer type ofthe communications based on a user selection or input. As discussed inmore detail below, the block transfer type defines the particularprotocol for transferring chucks or blocks of remote input/output (ROI)data between the remote device emulation appliance 102 and the masterprogrammable logic controller 104. Of course, other communicationparameters may be set in block 406 including, for example, the InternetProtocol (IP) address of the remote device emulation appliance, anysubnet masking, and/or other communication parameters.

The user may select, set, or otherwise supply the communicationinterface settings using any suitable user interface input mechanismsuch as a drop-down window, data entry cell, or other data entrytechnology. For example, as shown in FIG. 7, the remote device emulationappliance 102 may generate a user interface 700 for display on theremote computer 170 during configuration. The illustrative userinterface 700 includes a baud rate drop-down window 702, which the usermay interact with to select a baud rate from a list of possible choicesdisplayed in the drop-down window 702. Similarly, the illustrative userinterface 700 includes a block transfer type drop-down window 704 fromwhich the user may select a block transfer type from a list of possiblechoices displayed in the drop-down window 704.

Referring back to FIG. 4, if no communication interface settings are tobe configured in block 408 or after such configuration in block 410, themethod 400 advances to block 416 in which the remote device emulationappliance 102 determines whether the user desires to configure drivesettings of one or more drives 106 controlled by the remote deviceemulation appliance 102 (e.g., based on a user-supplied request orinput). If not, the method 400 loops back to block 406 in which theremote device emulation appliance 102 again determines whether the userdesires to configure any additional settings of the remote deviceemulation appliance 102. However, if the remote device emulationappliance 102 determines that user desires to configure drive settingsin block 416, the method 400 advances to block 418 in which the remotedevice emulation appliance 102 sets the drive type of one or more of thedrives 106 based on a user selection or input. That is, the user mayselect or define the type of drive of each of the drives 106 based onthe physical type, model, or other identification data of the drive 106.To do so, as shown in FIG. 7, the user may select the drive type from adrive type drop-down window 706 for the particular drive 106 ofinterest. As also shown in FIG. 7, the illustrative user interface 700includes a row 720 of adjustable or settable drive settings for eachdrive 106 supported by the remote device emulation appliance 102. Asdiscussed above, the illustrative remote device emulation appliance 102is capable of controlling up to six drives 106, but additional or fewerdrives 106 may be supported in other embodiments. Each row 720 includesvarious data entry widgets 706-718 for selecting or setting particulardrive settings for each corresponding drive 106 as discussed in moredetail below.

Referring back to FIG. 4, after the remote device emulation appliance102 has set the drive type for the present drive 106 of interest inblock 418 based on the user input, the method 400 advances to block 420.In block 420, the remote device emulation appliance 102 determineswhether the user desires to set a drive alias for the present drive 106.Each drive alias may be embodied as a “nickname” or other identifierthat uniquely identifies each particular drive 106, which may improvethe ease of managing drives 106 of the same type. If the remote deviceemulation appliance 102 determines that the user desires to set a drivealias for the present drive 106, the method 400 advances to block 422 inwhich the remote device emulation appliance 102 sets the drive alias forthe present drive 106 based on user input. For example, the user maytype in the desired drive alias or select a pre-defined alias via theuser interface 700 (see, e.g., FIG. 9).

After the remote device emulation appliance 102 has set the desireddrive alias in block 422 or if no drive alias is desired, the method 400advances to block 424 of FIG. 5. In block 424, the remote deviceemulation appliance 102 determines whether to auto-configure drivesettings based on the drive type of the present drive 106 selected inblock 418. For example, the remote device emulation appliance 102 may beconfigured to automatically configure drive settings based on theselected drive type or may do so in response to a user's instruction orselection. If so, the method 400 advances to block 426 in which theremote device emulation appliance 102 retrieves configuration data fromthe data storage 222 based on the selected type of drive 106, whichincludes predefined settings for the present drive 106. Subsequently, inblock 428, the remote device emulation appliance 102 configures thedrive settings for the present drive 106 using the retrievedconfiguration data. The drive settings may include any drive operationalparameter of the drive 106 that may be configured or otherwise set suchas the communication adaptor, drive profile, drive address, rack number,starting slot, block transfer type, and/or other operational parameter'sas discussed below.

After the remote device emulation appliance 102 has configured theinitial drive settings in block 428 or if auto-configuration of drivesettings is not desired, the method 400 advances to block 430 in whichthe user may manually configure and/or update drive settings of thepresent drive 106. For example, in block 432, the remote deviceemulation appliance 102 may set a communication adaptor for the presentdrive 106 based on a user's selection or input. The communicationadaptor defines the type of communication protocols that will be used bythe remote device emulation appliance 102 to communicate with thepresent drive 106. In some embodiments, the available communicationadaptors may be based on the drive type set in block 418. In block 434,the remote device emulation appliance 102 may set a drive profile forthe present drive 106 based on a user's selection or input. The driveprofile defines a main control word and status word(s), along with thespecific bit order of each. As discussed in more detail below, thecontrol and status words facilitate configuration and monitoring of thedrive. For example, the control word is transmitted by the masterprogrammable logic controller 104 to the corresponding drive via theremote device emulation appliance 102 to control the various stats ofthe drive. The status word is transmitted by drive to the masterprogrammable logic controller 104 via the remote device emulationappliance 102 to provide information related to the drive to the masterprogrammable logic controller 104. The drive profile may also includevarious reference values, such as a drive speed and/or torque referencefor the drive.

In block 436, the remote device emulation appliance 102 may set anaddress for the present drive 106 based on a user's selection or input.The address (e.g., an Internet Protocol address) defines the logicallocation on a network of the present drive 106 and is used by the remotedevice emulation appliance 102 to communicate with the present drive106. In block 438, the remote device emulation appliance 102 may set arack number for the present drive 106 based on a user's selection orinput. The rack number defines the logical rack to which the presentdrive 106 belongs. For example, all drives 106 having the same racknumber belong to the same logical rack. Similarly, in block 440, theremote device emulation appliance 102 may set a starting slot of thecorresponding rack for the present drive 106 based on a user's selectionor input. The starting slot identifies the slot of the logical rack fromwhich the present drive 106 will be mapped. Depending on otherconfigured settings and drives 106, the available valid starting slotsfor a particular drive 106 may change.

The user may select or set each of the drive settings discussed aboveusing any suitable input mechanism of the user interface 700. Forexample, as shown in FIG. 7, the illustrative user interface 700includes a communication adaptor drop-down window 708, a drive profiledrop-down window 710, a drive address window 712, a rack number window714, and a start slot drop-down window 716 for each drive 106 managed bythe remote device emulation appliance 102. A user may select or enterthe appropriate drive setting data in each of the windows 708-716. Asdiscussed above, the available settings in some of the windows 708-716may be restricted, updated, or modified based on other settings of thepresent drive 106 and/or other drives 106.

As the user configures (or the remote device emulation appliance 102auto-configures) the drive settings for each drive 106, correspondingdrive setting data is displayed to the user in a validation window 750.For example, as shown in FIG. 8, the illustrative validation window 750indicates that various data parameters of a Drive1 have been assigned tocorresponding slots of rack 1 and various data parameters of a Drive2have been assigned to corresponding slots of rack 2. The validationwindow 750 allows the user to visually verify the drive settings, aswell as indicate to the user any invalid configurations as discussed inmore detail below.

Referring back to FIG. 5, after the initial drive settings have beenconfigured or updated in block 430, the method 400 advances to block 442in which the remote device emulation appliance 102 determines whetherthe present drive 106 is to emulate a legacy drive. As discussed above,the remote device emulation appliance 102 may emulate legacy drives suchthat the present drive 106 appears as the emulated legacy drive to themaster programmable logic controller 104. By emulating a legacy drive, anewer or different drive 106 may be used in the system 100 withoutreprogramming the master programmable logic controller 104 and/orrewiring of the system 100.

If drive emulation is not desired, the method 400 advances to block 444in which the remote device emulation appliance 102 enables or disablesblock transfer for the present drive 106 based on a user selection orinput. As discussed above, block transfer allows the remote deviceemulation appliance 102 and the master programmable logic controller 104to transfer information regarding the present drive 106 between eachother in larger chucks of data relative to non-block transfercommunication. A user may enable block transfer for the present drive106 by selecting block transfer from a block transfer drop-down window718 of the illustrative user interface 700 associated with the presentdrive 106 as shown in FIG. 7.

Referring back to FIG. 5, if block transfer is enabled, the remotedevice emulation appliance 102 may set the number of discrete words foreach block transfer for the present drive 106 based on a user selectionor input in block 446. For example, the user may select the number ofdiscrete words from a discrete word drop-down window 720 (see FIG. 8).The available number of discrete words may be defined or limited by thetype of drive profile selected in block 434. In block 448, the remotedevice emulation appliance 102 may set the number of addressablediscrete blocks for block transfer for the present drive 106 based on auser selection or input. For example, the user may select the number ofaddressable block from an addressable block drop-down window 722 (seeFIG. 8). Additionally, in block 450, the remote device emulationappliance 102 may set the block type for each addressable blockidentified in block 448 based on user input. For example, the user mayselect the block type for each addressable block via corresponding blocktype drop-down windows 724 (see FIG. 8). Of course, additional or otherparameters related to addressable blocks may be set via the userinterface 700.

Referring back to block 442 of FIG. 5, if the remote device emulationappliance 102 determines that drive emulation is desired, the method 400advances to block 452 in which initial drive emulation parameters areset. To do so, in block 454, the remote device emulation appliance 102may enable or disable reference/feedback words based on user input orselection. For example, the user may enable or disable thereference/feedback words from a reference drop-down window 730 of theillustrative user interface 700 (see FIG. 9). Additionally, in block456, the remote device emulation appliance 102 may enable or disablevarious datalink pairs (e.g., datalink pairs A, B, C, and/or D) s forthe present drive 106. To do so, the user may enable or disable eachdatalink pair via a corresponding datalink drop-down window 732 of theillustrative user interface 700 (see FIG. 9). The remote deviceemulation appliance 102 may also enable or disable last datalinktruncation based on user input or selection in block 458. If lastdatalink truncation is enabled, the remote device emulation appliance102 truncates the last data link pair to one word for the correspondingdrive 106. A user may enable or disable the datalink truncation for eachdrive 106 via a datalink truncation drop-down window 734 of theillustrative user interface 700 (see FIG. 9).

Referring back to FIG. 5, after the drive emulation parameters have beenconfigured in block 452 or the block transfer parameters have beenconfigured in block 444, the method 400 advances to block 460 of FIG. 6.In block 460, the remote device emulation appliance 102 determineswhether the user desires to configure another drive 106 managed by theremote device emulation appliance 102. If so, the method 400 loops backto block 418 of FIG. 4 in which the user may set the drive type for thenext drive 106 being configured. If not, the method 400 advances toblock 462 in which the drive settings for each configured drive 106 arevalidated. To do so, the remote device emulation appliance 102 mayutilize any algorithm and/or data, which may be stored in the datastorage 222, to validate any one or more drive settings for eachconfigured drive 106. For example, in block 464, the remote deviceemulation appliance 102 may check for any rack slot conflicts in thedrive settings. That is, the remote device emulation appliance 102 mayverify that only one drive has been assigned to each rack slot. Ofcourse, the remote device emulation appliance 102 may validateadditional or other drive settings in other embodiments. For example,the remote device emulation appliance 102 may ensure a particular driveoperational parameter setting is within a defined threshold or range ofvalues, the format of the drive setting is valid, and/or other aspectsor characteristics of the drive settings are valid.

In block 466, the remote device emulation appliance 102 determineswhether the present drive settings for each configured drive are valid.If so, the method 400 advances to block 468 in which the drive settingsare stored in the data storage 222. Additionally or alternatively, someof the drive settings, or conversion data based on such drive settings,may be stored in the communication conversion database 320. If, however,the remote device emulation appliance 102 determines that the drivesettings are not valid, the method 400 advances to block 470 in whichthe remote device emulation appliance 102 identifies any invalid drivesettings to the user. For example, in block 472, the remote deviceemulation appliance 102 may highlight those drive settings determined tobe invalid. After the invalid drive settings have been identified to theuser, the method 400 subsequently loops back to block 430 in which theuser may update the conflicting drive settings.

The remote device emulation appliance 102 may utilize any methodology toidentify or highlight invalid drive settings including changing thecolor, font type, or font characteristics of invalid drive settings. Forexample, in the illustrative embodiment of FIG. 10, both Drive1 andDrive 2 have been assigned to slots 0, 1, and 2 of Rack 1, which resultsin a slot conflict. To identify the conflict to the user, the remotedevice emulation appliance 102 highlights the corresponding data cellsof the validation window 750. Of course, in other embodiments, theremote device emulation appliance 102 may highlight or identify the slotconflicts using other identification methodologies as discussed above.

Referring now to FIG. 11, if drive emulation has been elected, theremote device emulation appliance 102 may execute a method 1100 forconfiguring additional parameters of the drive emulation. The method1100 begins with block 1102 in which the remote device emulationappliance 102 determines whether to implement drive emulation. Asdiscussed above, the user may enable or select drive emulation from auser interface generated on the remote computer 170 by the remote deviceemulation appliance 102. If drive emulation is enabled, the method 1100advances to block 1104 in which remote device emulation appliance 102identifies the legacy drive to emulate. To do so, a user may identifythe legacy drive by selecting the drive from a compatibility drown-downmenu 760 of the illustrative user interface 700 (see FIG. 9). In someembodiments, the available legacy drives may be predetermined based onavailable conversion configuration data and/or other criteria.

In block 1106, the remote device emulation appliance 102 retrievescommunication conversion data from the communication conversion database320 based on the identified legacy drive. The communication conversiondata may be embodied as or otherwise include any type of data useable bythe remote device emulation appliance 102 to convert communicationsreceived from the master programmable logic controller 104 and directedto a target drive 106 managed by the remote device emulation appliance102 from a format and/or protocol unusable by the target drive 106 to aformat and/or protocol usable by the target drive 106. Additionally, thecommunication conversion data may be embodied as or otherwise includeany type of data useable by the remote device emulation appliance 102 toconvert communications received from the target drive 106 and directedto the master programmable logic controller 104 from the format and/orprotocol usable by the target drive 106 to the format and/or protocolunusable by the target drive 106. For example, the conversion data mayinclude a set of rules for converting a control word received incommunications from the master programmable logic controller 104 from alegacy drive format to a target drive format usable by the target drive106. Similarly, the conversion data may include a set of rules forconverting a status word receive din communications from the targetdrive 106 from a target drive format usable by the target drive 106 to alegacy drive format unusable by the target drive 106, but useable by themaster programmable logic controller 104. In this way, and as discussedin more detail below, the remote device emulation appliance 102 mayemulate a legacy drive by converting communications between the masterprogrammable logic controller 104 and the target drive(s) 106.

In block 1108, the remote device emulation appliance 102 sets thecommunication conversion parameters to be used to convert communicationsusing the predefined communication conversion data retrieved in block1106. For example, in block 1110, the remote device emulation appliance102 may set the control word format and/or status word format conversionparameters used to convert control words from the legacy drive format tothe target drive format and convert status words from the target driveformat to the legacy drive format to thereby emulate the legacy drive asdiscussed below.

In some embodiments, the user may additional set configurable conversionparameters in block 1112. Such configurable conversion parameters mayinclude the conversion data retrieved in block 1106 (i.e., the user mayupdate or modify the predetermined conversion parameters) and/oradditional conversion parameters that may not be predefined. Forexample, in block 1114, the remote device emulation appliance 102 mayset the stop mode for the present drive 106 based on a user selection orinput. The stop mode defines stop profile for the particular drive(e.g., “ramp to stop,” “coast to stop,” “emergency stop,” etc.). Inblock 1116, the remote device emulation appliance 102 may set the logiccontrol for the present drive 106 based on a user selection or input.The logic control defines the meaning or impact of particular bits ofthe control word. In block 1118, the remote device emulation appliance102 may set the jog frequency for the present drive 106 based on a userselection or input. The jog frequency defines the frequency of rotationof the shaft of the present drive 106 during a jog movement. The jogfrequency may be represented in Hertz or revolutions per minute (RPM).In block 1120, the remote device emulation appliance 102 may set theMotor Operated Potentiometer (MOP) increment for the present drive 106based on a user selection or input. The MOP increment defines the amountof shaft rotation of the present drive 106 for each MOP increment.

Additionally, in block 1122, the remote device emulation appliance 102may set the MOP reference for the present drive 106 based on userselection or input. The MOP reference defines the initial value orsetting for the MOP control of the present drive 106. As with the jogfrequency, the MOP increment and reference may be represented in Hertzor RPMs. In block 1124, the remote device emulation appliance 102 mayset the adapter identifier control for the present drive 106 based on auser selection or input. The adapter identifier identifies thecommunication adapter for the present drive 106 selected in block 432 ofmethod 400. As the communication adapter may be previously defined, theadapter identifier may be automatically set or configured by the remotedevice emulation appliance 102 in some embodiments. In block 1126, theremote device emulation appliance 102 may set the scaling coefficientfor the present drive 106 based on a user selection or input. Thescaling coefficient defines the scaling between the speed reference asrepresented in the legacy drive format relative to the target driveformat (i.e., the scaling difference between the speed control of thelegacy drive relative to the target drive).

The user may select or set each of the configurable conversionparameters discussed above using any suitable input mechanism of theuser interface 700. For example, as shown in FIG. 12, the remote deviceemulation appliance 102 may present a compatibility interface 1200 tothe user via the remote computer 170. The illustrative compatibilityinterface 1200 includes a stop mode drop-down window 1202, a logiccontrol drop-down window 1204, a jog frequency data cell 1206, a MOPincrement data cell 1208, a MOP reference data cell 1210, and areference scaling coefficient data cell 1214 for each drive 106 managedby the remote device emulation appliance 102. A user may select or enterthe appropriate conversion data in each of the windows 1202-1214 foreach respective drive 106.

Referring back to FIG. 11, after the user has configured any additionalconversion parameters in block 1112, the communication conversion datais saved in the communication conversion database 320 in block 1128. Asdiscussed in more detail below, the communication conversion data may besubsequently retrieved by the remote device emulation appliance 102 tofacilitate conversion of communications between the master programmablelogic controller 104 and the drive(s) 106.

Referring now to FIG. 13, in use, the remote device emulation appliance102 may execute a method 1300 for facilitating communication between themaster programmable logic controller 104 and a target drive 106 managedby the remote device emulation appliance 102. The method 1300 beginswith block 1302 and 1304, which may be executed in parallel or otherwisecontemporaneously with each other. In block 1302, the remote deviceemulation appliance 102 determines whether a communication has beenreceived from the master programmable logic controller 104. If so, themethod 1300 advances to block 1306 in which the communication receivedfrom the master programmable logic controller 104 is converted from theremote input/output protocol used by the controller 104 to transmit thecommunication (e.g., a legacy drive format) to a drive protocol usableby the target drive 106 to which the communication is directed. That is,as discussed above, the remote device emulation appliance 102 mayconvert the received communication from a format or protocol unusable bythe target drive (e.g., the legacy drive format) to a format or protocolusable by the target drive. To do so, in some embodiments, the remotedevice emulation appliance 102 may retrieve communication conversiondata from the communication conversion database 320 in block 1308. Asdiscussed above, the communication conversion data may include a set ofrules for converting the communications from the legacy drive format orprotocol to the target drive format or protocol. As such, in block 1310,the remote device emulation appliance 102 may convert a control wordincluded in the communication received from the master programmablelogic controller 104 from a legacy drive format unusable by the targetdrive 106 (e.g., a drive format configured for a legacy drive) to atarget drive format usable by the target drive 106 based on thecommunication conversion data. Additionally, in some embodiments inblock 1312, the remote device emulation appliance 102 may convert driveoperational parameters (e.g., a speed control instruction) from thelegacy drive format unusable by the target drive 106 to a drive formatusable by the target drive 106 based on the communication conversiondata and drive settings of the target drive 106.

After the remote device emulation appliance 102 has converted thecommunication from the remote input/output protocol to the driveprotocol in block 1306, the method 1300 advances to block 1314. In block1314, the remote device emulation appliance 102 transmits the convertedcommunication to the target drive 106 to control operation of the drive106. For example, the communication may include a control word convertedfrom the legacy drive format to the target drive format that dictatesoperation of the target drive 106. After the remote device emulationappliance 102 transmits the converted communication to the target drivein block 1314, the method 1300 loops back to blocks 1302 and 1304 tomonitor for additional communications.

Referring back to block 1304, the remote device emulation appliance 102also monitors for communications received from one or more of the drives106 managed by the appliance 102. If a communication is received from atarget drive 106, the method 1300 advances to block 1316 in which thecommunication received from the target drive 106 is converted from thedrive protocol to the remote input/output protocol (e.g., a legacy driveformat) used by master programmable logic controller 104. That is, asdiscussed above, the remote device emulation appliance 102 may convertthe received communication from a format or protocol usable by thetarget drive 106 to a format or protocol unusably by the target drive106 (e.g., the legacy drive format). To do so, in some embodiments, theremote device emulation appliance 102 may retrieve communicationconversion data from the communication conversion database 320 in block1318. As discussed above, the communication conversion data may includea set of rules for converting the communications from the target driveformat or protocol to a legacy drive format or protocol. As such, inblock 1320, the remote device emulation appliance 102 may convert astatus word included in the communication received from the target drive106 from a target drive format usable by the target drive 106 to alegacy drive format unusable by the target drive 106 (e.g., a driveformat configured for a legacy drive) based on the retrievedcommunication conversion data. Additionally, in some embodiments inblock 1322, the remote device emulation appliance 102 may convert driveoperational parameters (e.g., a speed control instruction) from thetarget drive format usable by the target drive 106 to a legacy driveformat unusable by the target drive 106 based on the communicationconversion data and drive settings of the target drive 106.

After the remote device emulation appliance 102 has converted thecommunication from the drive protocol to the remote input/outputprotocol in block 1316, the method 1300 advances to block 1324. In block1324, the remote device emulation appliance 102 transmits the convertedcommunication to the master programmable logic controller 104. Forexample, the communication may include a status word converted from thetarget drive format to the legacy drive format that informs the masterprogrammable logic controller 104 of particular status of the targetdrive 106 and/or other remote input. After the remote device emulationappliance 102 transmits the converted communication to the target drivein block 1324, the method 1300 loops back to blocks 1302 and 1304 tomonitor for additional communications.

In this way, the remote device emulation appliance 102 is capable ofconverting communications between the master programmable logiccontroller 104 and target drives 106 managed by the remote deviceemulation appliance 102. As such, newer drives 106 and/or drives 106having communication formats or protocols different from those of thelegacy drives for which the master programmable logic controller 104 iscurrently programmed to control may be used with the controller 104without the need to reprogram the controller 104 (or otherwise reducingthe amount of required reprogramming) and/or otherwise rewire the system100. As described above, the disclosed technologies provide a diagnostictool set that facilitates offline configuration and testing to insurethe appliance provides the desired monitoring and control withoutsignificant disruption of operations. The disclosed technologies alsoprovide a factory reset to factory defaults for a clean restart ofconfiguration if desired or required.

1. A method for facilitating communication between a master programmablelogic controller and a target drive, the method comprising: receiving,by a remote device emulation appliance, a first communication from themaster programmable logic controller over a remote input/outputcommunication link, wherein the first communication is formattedaccording to a remote input/output protocol unusable by the targetdrive; converting, by the remote device emulation appliance, the firstcommunication from the remote input/output protocol to a drive protocolusable by the target drive; and transmitting, by the remote deviceemulation appliance, the converted communication to the target drive tocontrol an operation of the target drive.
 2. The method of claim 1,wherein converting the first communication comprises converting, by theremote device emulation appliance, the communication from a remoteinput/output protocol configured for use by a legacy drive to the driveprotocol usable by the target drive.
 3. The method of claim 1, whereinconverting the first communication comprises converting, by the remotedevice emulation appliance, a format of a control word included in thefirst communication from a legacy drive format usable by a legacy driveto a target drive format usable by the target drive.
 4. The method ofclaim 1, wherein converting the first communication comprisesconverting, by the remote device emulation appliance, drive operationalparameters included in the communication from a legacy drive formatusable by a legacy drive to a target drive format usable by the targetdrive.
 5. The method of claim 1, wherein the converted communicationcomprises a first converted communication and further comprising:receiving, by the remote device emulation appliance, a secondcommunication from the target drive in response to the first convertedcommunication, wherein the second communication is formatted accordingto the drive protocol; converting, by the remote device emulationappliance, the second communication from the drive protocol to theremote input/output protocol; and transmitting the converted secondcommunication to the master programmable logic controller.
 6. The methodof claim 5, wherein converting the second communication comprisesconverting, by the remote device emulation appliance, a format of astatus word included in the second communication from a target driveformat usable by the target drive to a legacy drive format usable by alegacy drive.
 7. The method of claim 1, further comprising: receiving,by the remote device emulation appliance, a selection of a type of thetarget drive; receiving, by the remote device emulation appliance,configuration data from a user of the remote device emulation appliance,the configuration data comprising settings for drive operationalparameters of the target drive; setting, by the remote device emulationappliance, the drive operational parameters of the target drive based onthe received configuration data; determining, by the remote deviceemulation appliance, whether each of the set drive operationalparameters is valid; and visually identifying a first drive operationalparameter of the set drive operational parameters in response to adetermination that the first drive operational parameter is invalid. 8.The method of claim 1, further comprising: receiving, by the remotedevice emulation appliance, a selection of a legacy drive to be emulatedby the target drive; and retrieving, by the remote device emulationappliance, communication conversion data based on the selected legacydrive, wherein the communication conversion data defines conversionparameters for converting a communication from a legacy drive formatuseable by the legacy drive to a target drive format usable by thetarget drive.
 9. A remote device emulation appliance for facilitatingcommunication between a master programmable logic controller and adrive, the remote device emulation appliance comprising: a communicationcircuity configured to receive a first communication from the masterprogrammable logic controller over a remote input/output communicationlink, wherein the first communication is formatted according to a remoteinput/output protocol unusable by the target drive; and a communicationconversion circuity configured to convert the first communication fromthe remote input/output protocol to a drive protocol usable by thetarget drive, wherein the communication circuity is further configuredto transmit the converted communication to the target drive to controlan operation of the target drive.
 10. The remote device emulationappliance of claim 9, wherein to convert the first communicationcomprises to convert the first communication from a remote input/outputprotocol configured for use by a legacy drive to the drive protocolusable by the target drive.
 11. The remote device emulation appliance ofclaim 9, wherein to convert the first communication comprises to converta format of a control word included in the first communication from alegacy drive format usable by a legacy drive to a target drive formatusable by the target drive.
 12. The remote device emulation appliance ofclaim 9, wherein to convert the first communication comprises to convertdrive operational parameters included in the communication from a legacydrive format usable by a legacy drive to a target drive format usable bythe target drive.
 13. The remote device emulation appliance of claim 9,wherein the converted communication comprises a first convertedcommunication, and wherein: the communication circuity is configured toreceive a second communication from the target drive in response to thefirst converted communication, wherein the second communication isformatted according to the drive protocol, the communication conversioncircuity is configured to convert the second communication from thedrive protocol to the remote input/output protocol, and thecommunication circuity is further configured to transmit the convertedsecond communication to the master programmable logic controller. 14.The remote device emulation appliance of claim 13, wherein to convertthe second communication comprises to convert a format of a status wordincluded in the second communication from a target drive format usableby the target drive to a legacy drive format usable by a legacy drive.15. The remote device emulation appliance of claim 13, furthercomprising an initialization circuity and validation circuitry, whereinthe initialization circuitry is configured to: receive a selection of atype of the target drive; receive configuration data from a user of theremote device emulation appliance, the configuration data comprisingsettings for drive operational parameters of the target drive; and setthe drive operational parameters of the target drive based on thereceived configuration data, and wherein the validation circuitry isconfigured to: determine whether each of the set drive operationalparameters is valid, and visually identify a first drive operationalparameter of the set drive operational parameters in response to adetermination that the first drive operational parameter is invalid. 16.The remote device emulation appliance of claim 13, further comprising aninitialization circuity configured to: receive a selection of a legacydrive to be emulated by the target drive; and retrieve communicationconversion data based on the selected legacy drive, wherein thecommunication conversion data defines conversion parameters forconverting a communication from a legacy drive format useable by thelegacy drive to a target drive format usable by the target drive. 17.One or more non-transitory, machine-readable storage media comprising aplurality of instructions stored thereon that, in response to execution,cause a remote device emulation appliance to: receive a firstcommunication from a master programmable logic controller over a remoteinput/output communication link, wherein the first communication isformatted according to a remote input/output protocol unusable by thetarget drive; convert the first communication from the remoteinput/output protocol to a drive protocol usable by the target drive;and transmit the converted communication to the target drive to controlan operation of the target drive.
 18. The one or more non-transitory,machine-readable storage media of claim 17, wherein to convert the firstcommunication comprises to convert the first communication from a remoteinput/output protocol configured for use by a legacy drive to the driveprotocol usable by the target drive.
 19. The one or more non-transitory,machine-readable storage media of claim 17, wherein to convert the firstcommunication comprises to convert a format of a control word includedin the first communication from a legacy drive format usable by a legacydrive to a target drive format usable by the target drive.
 20. The oneor more non-transitory, machine-readable storage media of claim 17,wherein to convert the first communication comprises to convert driveoperational parameters included in the communication from a legacy driveformat usable by a legacy drive to a target drive format usable by thetarget drive.
 21. The one or more non-transitory, machine-readablestorage media of claim 17, wherein the converted communication comprisesa first converted communication, and wherein the plurality ofinstructions further cause the remote device emulation appliance to:receive a second communication from the target drive in response to thefirst converted communication, wherein the second communication isformatted according to the drive protocol, convert the secondcommunication from the drive protocol to the remote input/outputprotocol, and transmit the converted second communication to the masterprogrammable logic controller.
 22. The one or more non-transitory,machine-readable storage media of claim 21, wherein to convert thesecond communication comprises to convert a format of a status wordincluded in the second communication from a target drive format usableby the target drive to a legacy drive format usable by a legacy drive.23. The one or more non-transitory, machine-readable storage media ofclaim 17, wherein the plurality of instructions further cause the remotedevice emulation appliance to: receive a selection of a type of thetarget drive; receive configuration data from a user of the remotedevice emulation appliance, the configuration data comprising settingsfor drive operational parameters of the target drive; set the driveoperational parameters of the target drive based on the receivedconfiguration data; determine whether each of the set drive operationalparameters is valid; and visually identify a first drive operationalparameter of the set drive operational parameters in response to adetermination that the first drive operational parameter is invalid. 24.The one or more non-transitory, machine-readable storage media of claim17, wherein the plurality of instructions further cause the remotedevice emulation appliance to: receive a selection of a legacy drive tobe emulated by the target drive; and retrieve communication conversiondata based on the selected legacy drive, wherein the communicationconversion data defines conversion parameters for converting acommunication from a legacy drive format useable by the legacy drive toa target drive format usable by the target drive.